Hierarchy tree-based quality of service classification for packet processing

ABSTRACT

In one embodiment, a method comprises receiving a packet of a number of packets for storage into an egress port. The egress port has a number of queues associated with nodes of a hierarchy tree. The hierarchy tree has a level of nodes associated with contexts for the number of packets. The method also includes storing the packet into a queue of the number of queues of the egress port based the associated node within the hierarchy tree.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. provisional patentapplication No. 60/407,315 entitled “Hierarchy Tree-Based Quality ofService Classification for Packet Processing,” filed Aug. 30, 2002.

FIELD OF THE INVENTION

The invention relates to the field of communications. More specifically,the invention relates to hierarchy tree-based quality of serviceclassification for packet processing.

BACKGROUND OF THE INVENTION

Maintaining efficient flow of information over data communicationnetworks is becoming increasingly important in today's economy.Communications networks are evolving toward a connectionless model froma model whereby the networks provide end-to-end connections betweenspecific points. In a network which establishes specific end-to-endconnections to service the needs of individual applications, theindividual connections can be tailored to provide a desired bandwidthfor communications between the end points of the connections. This isnot possible in a connectionless network. The connectionless model isdesirable because such a model saves the overhead implicit in setting upconnections between pairs of endpoints and also provides opportunitiesfor making more efficient use of the network infrastructure throughstatistical gains. Many networks today provide connectionless routing ofdata packets, such as Internet Protocol (“IP”) data packets, over anetwork which includes end-to-end connections for carrying data packetsbetween certain parts of the network. The end-to-end connections may beprovided by technologies such as Asynchronous Transfer Mode (“ATM”),Time Division Multiplexing (“TDM”) and Sychronous Optical Network(SONET) and Synchronous Digital Hierarchy (SDH).

A Wide Area Network (“WAN”) is an example of a network used to provideinterconnections capable of carrying many different types of databetween geographically separated nodes. For example, the same WAN may beused to transmit video images, voice conversations, e-mail messages,data to and from database servers, and so on. Some of these servicesplace different requirements on the WAN.

A typical WAN comprises a shared network which is connected by accesslinks to two or more geographically separated customer premises. Each ofthe customer premises may include one or more devices connected to thenetwork. More typically, each customer premise has a number of computersconnected to a local area network (“LAN”). The LAN is connected to theWAN access link at a service point. The service point is generally at a“demarcation” unit or “interface device” which collects data packetsfrom the LAN which are destined for transmission over the WAN and sendsthose packets across the access link. The demarcation unit also receivesdata packets coming from the WAN across the access link and forwardsthose data packets to destinations on the LAN. One. type of demarcationunit may be termed an ESP (Enterprise Service Point).

A network service is dependent on the amount of data it can send andreceive from a source device to one or more destination devices.Therefore, the quality of a network service is dependent on the amountof network resources (such as uptime, outages, bandwidth, delay, loss,and jitter) the network can utilize to transfer its data. However, in aconventional IP network, all network services share all the networkresources on a first come, first serve (“best effort”) basis. This maybe detrimental to some network services since some services require morenetwork resources than other services.

For example, a typical video conferencing service requires much moredata to be sent than a typical e-mail service. Transmitting a videosignal for a videoconference requires fairly large bandwidth, shortdelay (or “latency”), small jitter, and reasonably small data lossratio. An e-mail service requires far less network resources than avideo conferencing service because the e-mail service often hasrelatively little data to send to its destinations and it is generallyacceptable if an e-mail transmission is slightly delayed in transiting anetwork. Transmitting e-mail messages or application data can generallybe done with lower bandwidth but can tolerate no data loss. Furthermore,it is not usually critical that e-mail be delivered instantly, so e-mailservices can usually tolerate longer latencies and lower bandwidth thanother services. In addition, the e-mail service requires only enoughnetwork resources to send data in a single direction. Conversely, thetypical video conferencing service requires enough network resources tosend data constantly and seamlessly in two directions. This may berequired if all participants in the video conference want to see eachother, and thus requires an individual's image to be sent to the otherparticipants and the other participant's images to be received.

If the network resources are shared in a best effort fashion betweenthese and other types of network services, the e-mail service willdeliver e-mail extremely fast, but the video conferencing service wouldnot be able to display a very clear picture. What is desired is to havea policy.where the network resources utilization is weighted such thatthe video conferencing service receives more network resources thane-mail services.

Typically, an enterprise which wishes to link its operations by a WANobtains an unallocated pool of bandwidth for use in carrying data overthe WAN. While it is possible to vary the amount of bandwidth availablein the pool (by purchasing more bandwidth on an as-needed basis), thereis no control over how much of the available bandwidth is taken by eachapplication.

Again, guaranteeing the Quality of Service (“QoS”) needed byapplications which require low latency is typically done by dedicatingend-to-end connection-oriented links to each application. This tends toresult in an inefficient allocation of bandwidth. Network resourceswhich are committed to a specific link are not readily shared, even ifthere are times when the link is not using all of the resources whichhave been allocated to it. Thus committing resources to specificend-to-end links reduces or eliminates the ability to achievestatistical gains. Statistical gains arise from the fact that it is veryunlikely that every application on a network will be generating amaximum amount of network traffic at the same time.

If applications are not provided with dedicated end-to-end connectionsbut share bandwidth, then each application can, in theory, share equallyin the available bandwidth. In practice, however, the amount ofbandwidth available to each application depends on things such as routerconfiguration, the location(s) where data for each application entersthe network, the speeds at which the application can generate the datathat it wishes to transmit on the network and so on. The result is thatbandwidth may be allocated in a manner that bears no relationship to therequirements of individual applications or to the relative importance ofthe applications. There are similar inequities in the latencies in thedelivery of data packets over the network.

The term “Quality of Service” is used in various different ways. Ingeneral, QoS refers to a set of parameters which describe the requiredtraffic characteristics of a data connection. The term “QoS” generallyrefers to a set of one or more of the following interrelated parameterswhich describe the way that a data connection treats data packetsgenerated by an application: a minimum bandwidth, a maximum delay, amaximum loss and jitter. A minimum bandwidth is a minimum rate at whicha data connection should be capable of forwarding data originating fromthe application. The data connection might be incapable of forwardingdata at a rate faster than the minimum bandwidth but should be capableof forwarding data at a rate equal to the rate specified by the minimumbandwidth. The maximum delay is a maximum time taken for data from anapplication to completely traverse the data connection. QoS requirementsare met only if data packets traverse the data connection in a timeequal to or shorter than the maximum delay. The maximum loss is amaximum fraction of data packets from the application which may not besuccessfully transmitted across the data connection. Jitter is a measureof how much variation there is in the delay experienced by differentpackets from the application being transmitted across the dataconnection. In an ideal case, where all packets take exactly the sameamount of time to traverse the data connection, the jitter is zero.Jitter may be defined, for example, as any one of various statisticalmeasures of the width of a distribution function which expresses theprobability that a packet will experience a particular delay intraversing the data connection. Different applications require differentlevels of QoS.

Recent developments in core switches for WANs have made it possible toconstruct WANs capable of quickly and efficiently transmitting vastamounts of data. There is a need for a way to provide network users withcontrol over the QoS provided to different data services which may beprovided over the same network.

Service providers who provide access to WANs wish to provide theircustomers with “Service Level Agreements” rather than raw bandwidth. AService Level Agreement is an agreement between a service provider and acustomer that defines the level of service that will be provided foreach particular type of application. This will permit the serviceproviders to take advantage of statistical gain to more efficiently usethe network infrastructure while maintaining levels of QoS thatcustomers require. To do this, the service providers need a way tomanage and track usage of these different services.

Applications connected to a network generate packets of data fortransmission on the network. In providing different levels of service itis necessary to be able to sort or “classify” data packets from one ormore applications into different classes which will be accordeddifferent levels of service. The data packets can then be transmitted ina way which maintains the required QoS for each application. Datapackets generated by one or more applications may belong to the sameclass.

SUMMARY OF THE INVENTION

A method and apparatus for hierarchy tree-based quality of serviceclassification for packet processing are described. In one embodiment, amethod comprises receiving a packet of a number of packets for storageinto an egress port. The egress port has a number of queues associatedwith nodes of a hierarchy tree. The hierarchy tree has a level of nodesassociated with contexts for the number of packets. The method alsoincludes storing the packet into a queue of the number of queues of theegress port based the associated node within the hierarchy tree.

In an embodiment, a network element comprises a traffic card thatincludes an egress port. The egress port is to include a number ofegress queues to store a number of data packets. The network elementalso includes a forwarding card. The forwarding card includes a memoryto store a port tree having a context level of nodes, wherein each nodeat the context level is associated with a context for the number of datapackets. The forwarding card also includes a forwarding engine to storea data packet of the number of data packets into an egress queue of thenumber of egress queues based on the context of the data packet.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention may be best understood by referring to thefollowing description and accompanying drawings which illustrate suchembodiments. The numbering scheme for the Figures included herein aresuch that the leading number for a given element in a Figure isassociated with the number of the Figure. For example, system 100 can belocated in FIG. 1. However, element numbers are the same for thoseelements that are the same across different Figures. In the drawings:

FIG. 1 illustrates a system for using a hierarchy tree in quality ofservice classification for packet processing, according to oneembodiment of the invention.

FIG. 2 illustrates a block diagram of a network element, according to anembodiment of the invention.

FIG. 3 illustrates a more detailed block diagram of a port on a trafficcard, according to one embodiment of the invention.

FIG. 4 illustrates a flow diagram for the storing of data packets into anumber of different queues for outputting across a number of differentoutput ports, according to one embodiment of the invention.

FIGS. 5A-5C illustrate hierarchy trees for quality of serviceclassification for processing of data packets, according to oneembodiment of the invention.

FIG. 6 illustrates a flow diagram for the outputting of data packetsfrom a number of different queues across a number of different ports ofa traffic card, according to one embodiment of the invention.

FIG. 7A illustrates a hierarchy tree, having a number of inactive nodes,for quality of service classification for processing of data packets,according to one embodiment of the invention.

FIG. 7B illustrates a bandwidth distribution across a hierarchy tree forquality of service classification for processing of data packets,according to one embodiment of the invention.

FIG. 8 illustrates a flow diagram for the distribution of the bandwidthfor the port based on a hierarchy tree, according to one embodiment ofthe invention.

FIG. 9 illustrates a flow diagram for the outputting of data from agiven port based on a hierarchy tree of data attributes, according toone embodiment of the invention.

FIG. 10 illustrates an output queue storing a number of packets,according to one embodiment of the invention.

FIGS. 11A-11B illustrate flow diagrams for the outputting of data from agiven port based on a hierarchy tree of data attributes, according toanother embodiment of the invention.

DETAILED DESCRIPTION

A method and apparatus for hierarchy tree-based quality of serviceclassification for packet processing are described. In the followingdescription, numerous specific details such as logic implementations,opcodes, means to specify operands, resourcepartitioning/sharing/duplication implementations, types andinterrelationships of system components, and logicpartitioning/integration choices are set forth in order to provide amore thorough understanding of the present invention. It will beappreciated, however, by one skilled in the art that the invention maybe practiced without such specific details. In other instances, controlstructures, gate level circuits and full software instruction sequenceshave not been shown in detail in order not to obscure the invention.Those of ordinary skill in the art, with the included descriptions, willbe able to implement appropriate functionality without undueexperimentation.

References in the specification to “one embodiment”, “an embodiment”,“an example embodiment”, etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to effect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

In the following description and claims, the terms “coupled” and“connected,” along with their derivatives, may be used. It should beunderstood that these terms are not intended as synonyms for each other.Rather, in particular embodiments, “connected” may be used to indicatethat two or more elements are in direct physical or electrical contactwith each other. “Coupled” may mean that two or more elements are indirect physical or electrical contact. However, “coupled” may also meanthat two or more elements are not in direct contact with each other, butyet still co-operate or interact with each other.

FIGS. 1-3 show block diagrams of systems and apparatus for hierarchytree-based quality of service classification for packet processing, inaccordance with embodiments of the invention. FIGS. 4, 6, 8-9 and 11show flow diagrams illustrating operations for hierarchy tree-basedquality of service classification for packet processing, according toembodiments of the invention. The operations of the flow diagram will bedescribed with references to the systems shown in the block diagrams.However, it should be understood that the operations of the flow diagramcould be performed by embodiments of systems and apparatus other thanthose discussed with reference to the block diagrams, and embodimentsdiscussed with reference to the systems could perform operationsdifferent than those discussed with reference to the flow diagram.

One aspect of the invention is the processing and storage of datapackets into a number of different output queues based on a hierarchytree-based quality of service classification, that are to besubsequently outputted from a number of different ports of a networkelement. Another aspect of the invention is the allocation of bandwidthfor the outputting of the data packets from the output queues based on ahierarchy tree-based quality of service classification. While these twoaspects can be used together, they are independent of each other. Inother words, the outputting of the data packets from the output queuesas described herein can be used irrespective of the method employed forthe storage of the data packets into the different output queues; andvice versa. In one embodiment, the hierarchy tree comprises a number ofdifferent levels that are associated with a number of differentattributes of the data packets being processed. In one embodiment, anattribute associated with the packet that is part of a level of such ahierarchy tree includes a context, which is described in more detailbelow. In an embodiment, an attribute associated with the packet that ispart of a level of such a hierarchy tree includes a tunnel that thepacket traverses through the network. In one embodiment, an attributeassociated with the packet that is art of a level of such a hierarchytree includes a subscriber from which the packet originated.

FIG. 1 illustrates a system for using a hierarchy tree in quality ofservice classification for packet processing, according to oneembodiment of the invention. As will be described in more detail below,a system 100 of FIG. 1 illustrates a system of communications that canbe based on a number of protocols and configurations. In particular, thesystem 100 of illustrates a system of communications that can be basedon a cable infrastructure, an infrastructure that employsDSL/Asynchronous Transfer Mode (ATM) and Ethernet, etc. These systemsare by way of example and not by way of limitation, as other systemsbased on other types of protocols and having other types ofconfigurations can incorporate embodiments of the invention. Forexample, embodiments of the inventions can be incorporated into awireless infrastructure, wherein wireless concentrators can route datafrom client devices into the network elements described herein.

With regard to FIG. 1, the system 100 comprises a number of subscriberdevices 102A-N, a network element 104 and a network 110. As shown, thesubscriber devices 102A-N are coupled to the network element 104 throughsubscriber connection 112A-N, respectively. The network element 104 iscoupled to the network 110. In one embodiment, the network element 104is coupled to other network elements within and coupled to the network110 through tunnels 114A-N. The tunnels 114A-N can be based on a numberof different types of protocols, including, but not limited to, Layer 2Tunneling Protocol (L2TP), Point-to-Point Tunneling Protocol (PPTP),etc.

The network element 104 includes a number of contexts 116A-N. In oneembodiment, a context is a logical coupling of a number of subscribers.For example, in one embodiment, an Internet Service Provider isassociated with a context. In another embodiment, subscribers beingreceived on a given interface(s) are associated with a context. In anembodiment, subscribers having a given connection rate, bandwidthminimums and/or maximums, etc are associated with a context.

In one embodiment, the network 110 is a local area network (LAN). In anembodiment, the network 110 is a wide area network (WAN). Further, thenetwork 110 may be a combination of different networks that couple thenetwork element 104 to other computing devices and network elementscoupled thereto. In one embodiment, the network element 104 includeslogic that enables the incorporation of a hierarchy tree into quality ofservice classification for packet processing. The operations of thesystem 100 illustrated in FIG. 1 will be described in more detail below.

FIG. 2 illustrates a block diagram of a network element, according to anembodiment of the invention. In particular, FIG. 2 illustrates a moredetailed block diagram of the network element 104, according to oneembodiment of the invention. As shown, the network element 104 includestraffic cards 250A-250N and a forwarding card 200. The network element104 is not limited to the number of traffic cards shown in FIG. 2, asthe network element 104 can include any of a number of different trafficcards.

In an embodiment, each of the traffic cards 250A-N include a processorand memory (not shown). The traffic cards 250A-N and the forwarding card200 are coupled together through system buses. This coupling together ofthe traffic cards 250 and the forwarding card 200 is representative of anumber of configurations to allow for the transferring of data packetsamong the different traffic cards 250. For example, in one embodiment,such system buses are representative of a mesh wherein each traffic card250 is connected to every other traffic card 250. In another example,such system buses are representative of a configuration wherein thetraffic cards 250 are coupled to the forwarding card 200. Accordingly,the data packets are received into a given traffic card 250 andtransmitted to the forwarding card 200, wherein the forwarding card 200includes a number of routing tables for forwarding the data packets tothe traffic card 250 from which the data packet is to be transmittedfrom the network element 104.

As shown, the forwarding card 200 comprises a processor 210, a memory220 and a forwarding engine 202. The processor 210 is coupled to theforwarding engine 202 and the memory 220. The forwarding engine 202 iscoupled to the memory 220. The processor 210 may comprise any suitableprocessor architecture. The forwarding card 200 for other embodimentsmay comprise more processors any of which may execute a set ofinstructions that are in accordance with embodiments of the presentinvention. The memory 220 stores a number of policy trees 204A-N and anumber of port trees 206A-N. As will be described in more detail below,the policy trees 204A-N and the port trees 206A-N are hierarchy treedata structures that are employed in the storage of data packets intoegress queues across a number of ports of the traffic cards 250A-N. Inan embodiment the policy trees 204A-N and the port trees 206A-N areemployed in the bandwidth distribution for the different egress queuesacross a number of ports of the traffic cards 250A-N. In one embodiment,a given port within one of the traffic cards 250 includes an associatedport tree 206. In one embodiment, a policy tree 204 is a generic datastructure, instances of which are different port trees 204. Accordingly,in one embodiment, a same policy tree 204 can be used as different porttrees 204 across different ports. In other words, two different portshaving a same quality of service policy can have two different porttrees 206 that are derived from a same policy tree. For example, in anobject-oriented environment, the policy trees 204 can be classes, whilethe port trees can be instances of such classes. Embodiments of the porttrees 206 are described in more detail below.

While FIG. 2 illustrates the policy trees 204A-N and the port trees206A-N being stored in a memory within the forwarding card 200,embodiments of the invention are not so limited. For example, in otherembodiments, the policy trees 204A-N and/or the port trees 206A-N can bestored within memories of the associated traffic cards 250A-N. Thememory 220 may store also store other data and/or instructions, forexample, for the forwarding card 200 and may comprise any suitablememory, such as a dynamic random access memory (DRAM) for example.

As will be described in more detail below, in one embodiment, theforwarding engine 202 provides for the storage of data packets intoegress queues across a number of ports of the traffic cards 250A-N andfor the outputting of data packets from such egress queues based on ahierarchy tree-based quality of service classification. While FIG. 2illustrates one forwarding engine 202 for such processing across thenumber of different traffic cards 250A-N, embodiments of the inventionare not so limited. In other embodiments, a number of differentforwarding engines 202 within the forwarding card 200 and/or the trafficcards 250A-N perform such processing. For example, in one embodiment,each traffic card 250A-N can include a forwarding engine 202.

In an embodiment, the forwarding engine 202 is a process or task thatcan reside within the memory 220 and/or the processor 210 and can beexecuted within the processor 210. However, embodiments of the inventionare not so limited, as the forwarding engine 202 can be different typesof hardware (such as digital logic) executing the processing describedtherein (which is described in more detail below). Accordingly, theforwarding card 200 may include a machine-readable medium on which isstored a set of instructions (i.e., software) embodying any one, or all,of the methodologies described herein. For example, software can reside,completely or at least partially, within the memory 220 and/or withinthe processor 210.

Moreover, the forwarding card 200 provides for buffering, packetprocessing and forwarding of data packets being received by the trafficcards 250A-N. In particular, as shown, the traffic cards 250A-N arecoupled to a number of data transmission lines, which are coupled toother network elements and/or computing devices. Accordingly, thetraffic cards 250A-N receive and transmit data traffic from and to datatransmission lines coupled thereto. Such data traffic is transmitted tothe forwarding card 200, where this traffic can be buffered, processedand/or forwarded to other traffic cards within the network element 104,as will be described in more detail below.

Further, the traffic card 250A includes a number of ports 252A-N, whilethe traffic card 250N includes a number of ports 254A-N. The ports252A-N and the ports 254A-N are representative of physical and/orlogical interfaces for receiving and transmitting data into and out fromthe traffic card 250A and the traffic card 250N.

FIG. 3 illustrates a more detailed block diagram of a port on a trafficcard, according to one embodiment of the invention. In particular, FIG.3 illustrates a more detailed block diagram of one of the ports 252/254on one of the traffic cards 250, according to one embodiment of theinvention. As shown, the ports 252/254 comprise a number of outputqueues 302A-N. In one embodiment, the output queues 302 are employed forstoring data packets that are to be outputted from the traffic cards250. Such operation is described in more detail below.

In particular, the operations for storing data packets into a number ofdifferent queues for outputting across a number of different outputports will now be described. In particular, FIG. 4 illustrates a flowdiagram for the storing of data packets into a number of differentqueues for outputting across a number of different output ports,according to one embodiment of the invention. The operation of the flowdiagram 400 will be described with reference to the exemplary systemsshown in FIGS. 1-3.

In block 402, a packet is received. With reference to the exemplaryembodiment of FIGS. 2 and 3, a first traffic card 250 receives a datapacket from an external source, such as a different network element, asubscriber computing device, etc. Control continues at block 404.

In block 404, the node within the port tree (for the egress port thatthe packet is to be outputted from) at the highest level associated withthe received packet is located. With reference to the exemplaryembodiment of FIGS. 2 and 3, the forwarding engine 202 locates the nodewithin the port tree 206 associated with the port that the data packetis to be output from. To help illustrate, assume that the data packet isreceived into an ingress port of the traffic card 250A. The data packetis transmitted to the forwarding card 200, wherein the forwarding engine202 determines that the data packet is to be outputted on the egressport 254A of the traffic card 250N (based on routing tables within theforwarding card 200 (not shown)). Accordingly, the forwarding engine 202retrieves the port tree 206 associated with the egress port 254A frommemory 220. Further, the forwarding engine 202 locates the node withinthe port tree 206 at the highest level associated with the receivedpacket.

To help illustrate, FIGS. 5A-5C illustrate hierarchy trees for qualityof service classification for processing of data packets, according toone embodiment of the invention. In one embodiment, the hierarchy treesillustrates in FIGS. 5A-5C are representative of the port trees 206 andthe policy trees 204. As shown, FIGS. 5A-5C illustrate that suchhierarchy trees are based on a combination of different attributesassociated with the data packets. In one embodiment, these hierarchytrees include a level for a context of a data packet. In an embodiment,these hierarchy trees include a level for a tunnel of a data packet. Inone embodiment, these hierarchy trees include a level for a subscriberof a data packet. Such attributes incorporated into the hierarchy treesare by way of example and not by way of limitation, as other attributesof the data packet can be incorporated therein. Other examples of datapacket attributes that can be incorporated into the hierarchy treeinclude the port/interface the data packet is received, the destinationof the data packet, etc. Further, as shown, the nodes of the hierarchytrees have associated percentages, which are percentages of theallocated bandwidth for the port relative to other sibling nodes. Thedistribution of the bandwidth and the outputting of data based on thesepercentages is described in more detail below.

FIG. 5A illustrates a hierarchy tree 500 that includes three levels: (1)a context level, (2) a tunnel level and (3) a subscriber level. Asshown, the hierarchy tree 500 includes a root 502 that includes a numberof children nodes at a context level. In particular, the root 502includes a context A node 504 (having a bandwidth percentage of 50%) anda context B node 506 (having a bandwidth percentage of 50%). The contextA node 504 includes a number of children nodes at a tunnel level. Inparticular, the context A node 504 includes a tunnel A node 508 (havinga bandwidth percentage of 25%) and a tunnel B node 510 (having abandwidth percentage of 25%). The context B node 506 includes a numberof children nodes at the tunnel level. In particular, the context B node506 includes a tunnel C node 512 (having a bandwidth percentage of 25%)and a tunnel D node 514 (having a bandwidth percentage of 50%).

The tunnel A node 508 includes a number of children nodes (that are leafnodes of the hierarchy tree 500) at a subscriber level. In particular,the tunnel A node 508 includes a subscriber A node 516 (having abandwidth percentage of 25%), a subscriber B node 518 (having abandwidth percentage of 25%), a subscriber C node 520 (having abandwidth percentage of 25%) and a subscriber D node 522 (having abandwidth percentage of 25%). The tunnel B node 510 includes a number ofchildren nodes (that are leaf nodes of the hierarchy tree 500) at thesubscriber level. In particular, the tunnel B node 510 includes asubscriber E node 524 (having a bandwidth percentage of 33⅓%), asubscriber F node 528 (having a bandwidth percentage of 33⅓%) and asubscriber G node 526 (having a bandwidth percentage of 33⅓%). Thetunnel C node 512 includes a number of children nodes (that are leafnodes of the hierarchy tree 500) at the subscriber level. In particular,the tunnel C node 512 includes a subscriber I node 532 (having abandwidth percentage of 50%) and a subscriber J node 530 (having abandwidth percentage of 50%). The tunnel D node 514 includes a number ofchildren nodes (that are leaf nodes of the hierarchy tree 500) at thesubscriber level. In particular, the tunnel D node 514 includes asubscriber K node 534 (having a bandwidth percentage of 50%) and asubscriber L node 536 (having a bandwidth percentage of 50%).

FIG. 5B illustrates a hierarchy tree 501 that includes two levels: (1) atunnel level and (2) a subscriber level. As shown, the hierarchy tree501 includes a root 540 that includes a number of children nodes at atunnel level. In particular, the root 540 includes a tunnel A node 542(having a bandwidth percentage of 50%) and a tunnel B node 544 (having abandwidth percentage of 50%). The tunnel A node 542 includes a number ofchildren nodes (that are leaf nodes of the hierarchy tree 501) at asubscriber level. In particular, the tunnel A node 542 includes asubscriber A node 546 (having a bandwidth percentage of 25%), asubscriber B node 548 (having a bandwidth percentage of 25%), asubscriber C node 550 (having a bandwidth percentage of 25%) and asubscriber D node 552 (having a bandwidth percentage of 25%). The tunnelB node 544 includes a number of children nodes (that are leaf nodes ofthe hierarchy tree 501) at the subscriber level. In particular, thetunnel B node 544 includes a subscriber E node 554 (having a bandwidthpercentage of 33⅓%), a subscriber F node 558 (having a bandwidthpercentage of 33⅓%) and a subscriber G node 556 (having a bandwidthpercentage of 33⅓%).

FIG. 5C illustrates a hierarchy tree 503 that includes two levels: (1) acontext level and (2) a subscriber level. As shown, the hierarchy tree503 includes a root 570 that includes a number of children nodes at acontext level. In particular, the root 570 includes a context A node 572(having a bandwidth percentage of 33⅓%), a context B node 574 (having abandwidth percentage of 33⅓%) and a context C node 576 (having abandwidth percentage of 33⅓%). The context A node 572 includes a numberof children nodes (that are leaf nodes of the hierarchy tree 503) at asubscriber level. In particular, the context A node 572 includes asubscriber A node 577 (having a bandwidth percentage of 25%), asubscriber B node 578 (having a bandwidth percentage of 25%), asubscriber C node 579 (having a bandwidth percentage of 25%) and asubscriber D node 580 (having a bandwidth percentage of 25%). Thecontext B node 574 includes a number of children nodes (that are leafnodes of the hierarchy tree 503) at the subscriber level. In particular,the context B node 574 includes a subscriber E node 581 (having abandwidth percentage of 33⅓%), a subscriber F node 582 (having abandwidth percentage of 33⅓%) and a subscriber G node 583 (having abandwidth percentage of 33⅓%). The context C node 576 includes a numberof children nodes (that are leaf nodes of the hierarchy tree 503) at thesubscriber level. In particular, the context C node 576 includes asubscriber H node 583 (having a bandwidth percentage of 25%), asubscriber I node 584 (having a bandwidth percentage of 25%), asubscriber J node 585 (having a bandwidth percentage of 25%) and asubscriber K node 586 (having a bandwidth percentage of 25%). Thehierarchy trees illustrated in FIGS. 5A-SC are by way of example and notby way of limitation, as embodiments of the invention can incorporatehierarchy trees having a lesser and/or greater number of levels.Further, embodiments of the invention can incorporate levels havingattributes that are different from those illustrated in FIGS. 5A-5C. Forexample, in one embodiment, a hierarchy tree could include a contextlevel and a tunnel level. In another embodiment, a hierarchy tree couldinclude a tunnel level and an interface level (related to the interfacethat the packet is received).

Using the hierarchy tree 500 of FIG. 5A and returning to the flowdiagram 400 of FIG. 4, to help illustrate the locating of the nodewithin the port tree at the highest level associated with the receivedpacket, assume that the data packet is received into an ingress port ofthe traffic card 250A. The data packet is transmitted to the forwardingcard 200, wherein the forwarding engine 202 determines that the datapacket is to be outputted on the egress port 254A of the traffic card250N (based on routing tables within the forwarding card 200 (notshown)). Accordingly, the forwarding engine 202 retrieves the port tree206 associated with the egress port 254A from the memory 220.

Further, the forwarding engine 202 begins traversal of the hierarchytree 500 at the root 502. The forwarding engine 202 checks the nodes atthe level below the root 502 (the highest level) and locates the node atthis level associated with the packet. In this example, the packetsbeing received are associated with a context (such as an InternetService Provider, etc.) In one embodiment, based on the egress circuitand/or tunnel, the forwarding engine 202 can retrieve attributesassociated with the packet including the context. Returning to theexample, the forwarding engine 202 compares the context of the packet tocontext A of the node 504. If the two contexts match, the forwardingengine 202 has located the node within the port tree at the highestlevel associated with the received packet. Conversely, if the twocontexts do not match, the forwarding engine 202 checks a different nodeat the highest level. Accordingly, the forwarding engine 202 comparesthe context of the packet to the context B of the node 506. Theforwarding engine 202 continues this traversal and comparison of thenodes at the highest level until a match is made with the context of thepacket. Control continues at block 406.

In block 406, a determination is made on whether the located node is anon-leaf node of the hierarchy tree being traversed. With reference tothe exemplary embodiment of FIG. 2, the forwarding engine 202 makes thisdetermination. In one embodiment, the forwarding engine 202 makes thisdetermination based on an attribute for this node identifying such nodeas a leaf or non-leaf node. In another embodiment, the forwarding engine202 makes this determination based on whether the located node has anychildren nodes.

In block 408, upon determining that the node is a non-leaf node, thenode within the port tree at the next level associated with the receivedpacket is located. With reference to the exemplary embodiment of FIG. 2,the forwarding engine 202 locates the node within the port tree 206 atthe level (below the level at a node was previously located) associatedwith the received packet.

Using the hierarchy tree 500 of FIG. 5A to help illustrate the locatingof the node within the port tree at the next level associated with thereceived packet, assume that the prior level wherein a node was locatedwas the context level. Accordingly, the forwarding engine 202 continuestraversal of the hierarchy tree 500 at the tunnel level. The forwardingengine 202 locates the node at this level associated with the packet. Inthis example, the packets being received are associated with a tunnelthat the packets are being transmitted through across the network (asdiscussed above). In one embodiment, the forwarding engine 202 canretrieve attributes associated with the packet including the tunnel.Returning to the example, the forwarding engine 202 compares the tunnelof the packet to tunnel A of the node 508. If the two tunnels match, theforwarding engine 202 has located the node within the port tree at thenext level associated with the received packet. Conversely, if the twotunnels do not match, the forwarding engine 202 checks a different nodeat this level. Accordingly, the forwarding engine 202 compares thetunnel of the packet to the tunnel B of the node 510. The forwardingengine 202 continues this traversal and comparison of the nodes at thislevel until a match is made with the tunnel of the packet. Controlcontinues at block 406.

As described, the process continues traversing the port tree for thispacket until the associated node for the current level is a leaf node.Returning to FIG. 5A to help illustrate, the forwarding engine 202 wouldlocate the associated node for the packet at the subscriber level, whichwould be a leaf node (as such nodes do not have children nodes).

In block 410, upon determining that the located node is a leaf node, adetermination is made of whether there are multiple queues associatedwith this located leaf node. With reference to the exemplary embodimentof FIG. 2, the forwarding engine 202 makes this determination. In oneembodiment, a leaf node within a port tree is associated with one to anumber of output queues that the packets are to be stored prior to beoutputting from the traffic card 250. For example, the output queues302A-302C are associated with the subscriber A node 516, while theoutput queues 302D-302H are associated with the subscriber B node 518,while the output queue 3021 is associated with the subscriber C node520, etc.

In block 412, upon determining that there are not multiple queuesassociated with this located leaf node, the packet is stored in the onequeue for this leaf node. With reference to the exemplary embodiment ofFIGS. 2 and 3, the forwarding engine 202 stores the packet into this onequeue associated with this node for the given port 250/254 for the giventraffic card 250 that the data packet is to be output from. The processof the storage of the data packet into the appropriate output queuebased on a hierarchy tree is complete.

In block 414, upon determining that there are multiple queues associatedwith this located leaf node, the queue among the multiple queues for thestorage of the packet is determined. With reference to the exemplaryembodiment of FIG. 2, the forwarding engine 202 makes thisdetermination. While any of a number of different approaches can beemployed in the determination of the queue for the storage of the datapacket, in one embodiment, the forwarding engine 202 employs theStochastic Fair Queuing (SFQ) algorithm for a determination of the queueof the number of queues that the data packet is to be stored. In anotherembodiment, the forwarding engine 202 determines the queue based on around robin order. Control continues in block 416.

In block 416, the packet is stored in the determined queue among themultiple queues for the leaf node. With reference to the exemplaryembodiment of FIGS. 2 and 3, the forwarding engine 202 stores the packetinto this determined queue associated with this leaf node for the givenport 250/254 for the given traffic card 250 that the data packet is tobe output from. The process of the storage of the data packet into theappropriate output queue based on a hierarchy tree is complete.

The operations for outputting data packets from a number of differentqueues across a number of different output ports of a traffic card willnow be described. In particular, FIG. 6 illustrates a flow diagram forthe outputting of data packets from a number of different queues acrossa number of different ports of a traffic card, according to oneembodiment of the invention. The operation of flow diagram 600 will bedescribed with reference to the exemplary systems shown FIGS. 1-3.

In block 602, the active nodes within the port tree are determined. Withreference to the exemplary embodiment of FIG. 2, the forwarding engine202 determines the active nodes within the port tree. To helpillustrate, FIG. 7A illustrates a hierarchy tree, having a number ofinactive nodes, for quality of service classification for processing ofdata packets, according to one embodiment of the invention. Inparticular, FIG. 7A illustrates the hierarchy tree 500 of FIG. 5A,wherein a number of the nodes are inactive. In one embodiment, a node isconsidered inactive when the associated queue(s) do not have datacurrently stored therein. As described above, in an embodiment, thehierarchy tree 500 is a data structure having a number of objects thatinclude a number of attributes. Accordingly, in one embodiment, a nodewithin the hierarchy tree 500 is an object that includes an attributeindicating whether the associated queue(s) for this node having datastored therein.

As shown in FIG. 7A, the subscriber A node 516 and the subscriber G node526 are inactive. Further, the subscriber K node 534 and the subscriberL node 536 are inactive. Because all of the leaf children nodes of thetunnel D node 514 are inactive, the tunnel D node 514 is consideredinactive. Therefore, the queue(s) associated with these leaf nodes arenot currently storing data packets to be outputted from the associatedport for this hierarchy tree.

Returning to FIG. 6 and using the hierarchy tree 500 illustrated in FIG.7A, the forwarding engine 202 traverses the hierarchy tree 500 anddetermines that the context A node 504, the context B node 506, thetunnel A node 508, the tunnel B node 510, the tunnel C node 512, thesubscriber B node 518, the subscriber C node 520, the subscriber D node522, the subscriber E node 524, the subscriber F node 528, thesubscriber I node 532 and the subscriber J node 530 are active nodes.

In block 604, the bandwidth for the port is distributed across thequeues associated with the active nodes of the port tree. With referenceto the exemplary embodiment of FIG. 2, the forwarding engine 202distributes the bandwidth for the port across the queues associated withthe active nodes of the port tree. Based on the example illustrated inFIG. 7A, the forwarding engine 202 distributes the bandwidth for theport across the queues associated with that the context A node 504, thecontext B node 506, the tunnel A node 508, the tunnel B node 510, thetunnel C node 512, the subscriber B node 518, the subscriber C node 520,the subscriber D node 522, the subscriber E node 524, the subscriber Fnode 528, the subscriber I node 532 and the subscriber J node 530. Thedistribution of the bandwidth for the port is described in more detailbelow in conjunction with FIG. 8.

In block 606, the data is outputted from the port based on thedistributed bandwidth using the port tree. With reference to theexemplary embodiment of FIG. 2, the forwarding engine 202 outputs thedata from the port based on the distributed bandwidth using the porttree. The outputting of the data from the port based on the distributedbandwidth using the port tree is described in more detail below inconjunction with FIGS. 9-11.

The operations for the distribution of the bandwidth for the port willnow be described. In particular, FIG. 8 illustrates a flow diagram forthe distribution of the bandwidth for the port based on a hierarchytree, according to one embodiment of the invention. The operation of theflow diagram 800 will be described with reference to the exemplarysystems shown FIGS. 1-3.

In block 802, a determination is made on whether there are any activenodes in the port tree for this port. With reference to the exemplaryembodiment of FIG. 2, the forwarding engine 202 makes this determinationon whether there are any active nodes in the port tree for this port. Asdescribed above in conjunction with the operation in block 602 of FIG.6, the forwarding engine 202 locates the active nodes within the porttree. Accordingly, based on this locating, the forwarding engine 202makes the determination whether the port tree include any active nodes.For example, in an embodiment, when there are no queues for the port forthis port tree that are currently storing data therein, all nodes forthis port tree are considered inactive. Upon determining that there areno active nodes in the port tree, the operation of the flow diagram 800is complete.

In block 804, upon determining that there are active nodes in the porttree, the bandwidth for the current port is allocated across the highestlevel of the port tree having active node(s). With reference to theexemplary embodiment of FIG. 2, the forwarding engine 202 allocates thebandwidth for the current port across the highest level of the port treehaving active node(s).

To help illustrate, FIG. 7B illustrates a bandwidth distribution acrossa hierarchy tree for quality of service classification for processing ofdata packets, according to one embodiment of the invention. Inparticular, FIG. 7B illustrates the hierarchy tree 500 of FIG. 7A with adistribution of bandwidth across the different active nodes of the tree.At the root node 502, a value of 400 is available for the associatedport for a given cycle. In one embodiment, this value is representativeof a number of megabits. This value is distributed to the context level(the highest level). As shown, the context A node 504 and the context Bnode are each to receive 50% of the bandwidth. Accordingly, a value of200 is available for the context A node 504, while a value of 200 isavailable for the context B node 506. Control continues at block 806.

Returning to FIG. 8, in block 806, a determination is made on whetherthe active node(s) at the current level of the port tree have activechildren nodes. With reference to the exemplary embodiment of FIG. 2,the forwarding engine 202 makes this determination on whether the activenode(s) at the current level of the port tree have active childrennodes. Returning to FIG. 7B to help illustrate, the forwarding engine202 determines whether the context A node 504 and the context B node 506have children nodes. In this example, the context A node 504 has twochildren nodes that are active: the tunnel A node 508 and the tunnel Bnode 510. Further, the context B node 506 has one child node that isactive: the tunnel C node 512.

In block 808, upon determining that the active node(s) at the currentlevel of the port tree do have children nodes that are active, thebandwidth is allocated across the active children node(s) for a firstactive node at the current level. With reference to the exemplaryembodiment of FIG. 2, the forwarding engine 202 allocates the bandwidthacross the active children node(s) for a first active node at thecurrent level of the port tree. Returning to FIG. 7B to help illustrate,assume that the context A node 504 is considered the first active nodeat the current level (the context level). Accordingly, the forwardingengine 202 allocates the bandwidth across the children nodes of node504: the tunnel A node 508 and the tunnel B node 510. As shown, thetunnel A node 508 and the tunnel B node 510 are each to receive 50% ofthe bandwidth allocated to its parent node: context A node 504.Therefore, the forwarding engine 202 assigns a value of 100 to both thetunnel A node 508 and the tunnel B node 510. Control continues at block810.

In block 810, a determination is made on whether other active nodes atthe current level of the port tree have active children nodes. Withreference to the exemplary embodiment of FIG. 2, the forwarding engine202 determines whether other active nodes at the current level of theport tree have active children nodes. Returning to FIG. 7B to helpillustrate, the forwarding engine 202 determines whether the contextlevel includes other active nodes that have active children nodes. Inthis example, the forwarding engine 202 determines that the context Bnode 506 has one active child node: the tunnel C node 512.

In block 812, upon determining that other active nodes at the currentlevel of the port tree have active children nodes, bandwidth isallocated across the active children node(s) for one of these activenodes at the current level. Returning to the exemplary embodiment ofFIG. 2, the forwarding engine 202 allocates the bandwidth across theactive children node(s) for one of these active children nodes at thecurrent level. Returning to FIG. 7B to help illustrate, the forwardingengine 202 allocates the bandwidth across the active child node for thecontext B node 506: the tunnel C node 512. As shown, even though thetunnel C node 512 is to receive 50% of the bandwidth allocated to itsparent node (the context B node 506), the forwarding engine 202allocates the entire bandwidth (200) to the tunnel C node 512 becausethe other children nodes are inactive. Control continues at block 810.This recursive operation of determining whether other active nodes atthe current level of the port tree have active children nodes as well asthe allocation of the bandwidth to such active children nodes continuesuntil the active nodes at the current level have been processed.

In block 814, upon determining that there are no other active nodes atthe current level of the port tree that have not been processed, thenext level of the port tree is assigned as the current level (forprocessing). Returning to the exemplary embodiment of FIG. 2, theforwarding engine 202 assigns the next level of the port tree as thecurrent level. Returning to the example shown in FIG. 7B to helpillustrate, the forwarding engine 202 assigns the tunnel level as thecurrent level. Control continues at block 806.

Accordingly, the forwarding engine 202 determines whether the activenodes of the current level have active children node(s), as describedabove. Returning to the example in FIG. 7B to help illustrate, theforwarding engine 202 determines whether the tunnel A node 508, thetunnel B node 510 or the tunnel C node 512 have active children nodes.Based on the operations described in blocks 806-814, the forwardingengine 202 allocates the bandwidth of the tunnel A node 508 to thesubscriber B node 518, the subscriber C node 520 and the subscriber Dnode 522 (each receiving a bandwidth value of 33⅓). This allocatedbandwidth value for the nodes 518-522 are greater because the subscriberA node 516 is inactive (does not have data in the associated queues forthis node).

Additionally, the forwarding engine 202 allocates the tunnel B node 510to the subscriber E node 524 and the subscriber F node 528 (eachreceiving a bandwidth value of 50). This allocated bandwidth value forthe nodes 524 and 528 is greater because the subscriber G node 526 isinactive. The forwarding engine 202 allocates the tunnel C node 512 tothe subscriber I node 532 and the subscriber J node 530 (each receivinga bandwidth value of 100). This allocated bandwidth value for the nodes530 and 532 is greater because the children nodes along with the tunnelD node 514 are inactive. As described, the bandwidth for a given port isallocated based on the associated port tree having nodes associated withdifferent attributes of the packets to be outputted. Further, thebandwidth for a given port is allocated such that only the nodes thatare active (having queues that have data packets or children nodes thathave queues that have data packets) receive bandwidth. Accordingly, thebandwidth for the given port is not unused. In one embodiment, thisallocation of the bandwidth is performed each time data packets are tobe outputted from the port.

The operations of outputting of data from a given port will now bedescribed. FIG. 9 illustrates a flow diagram for the outputting of datafrom a given port based on a hierarchy tree of data attributes,according to one embodiment of the invention. The operation of the flowdiagram 900 will be described with reference to the exemplary systemsshown FIGS. 1-3.

In block 902, a determination made of whether there are active leafnode(s) that are unprocessed for the current cycle. With reference tothe exemplary embodiment of FIG. 2, the forwarding engine 202 makes thedetermination of whether there are active leaf node(s) that areunprocessed for the current cycle. As described above, in an embodiment,the forwarding engine 202 traverses the port tree for the given port toidentify the current active nodes within the tree. Accordingly, in anembodiment, the forwarding engine 202 tracks whether active leaf nodeshave been processed in a current cycle. Upon determining that there areno active leaf node(s) that are unprocessed for the current cycle, theoperations of the flow diagram 900 are complete, thereby completing theoutputting of data for a given cycle for a port on a traffic card.

In block 904, upon determining that there are active leaf node(s) thatare unprocessed for the current cycle, an active leaf node that has notbeen processed is selected. With reference to the exemplary embodimentof FIG. 2, the forwarding engine 202 selects an active leaf node thathas not been processed. While the selection of an active leaf node(unprocessed) can be in one of a number of different orders ofprocessing of such nodes, in one embodiment, the forwarding engine 202selects the unprocessed active leaf nodes in an order such that thesibling active leaf nodes are processed sequentially. Returning to FIG.7B to help illustrate, in one embodiment, the subscriber B node 518, thesubscriber C node 520 and the subscriber D node 522 are processed insequential order. In other embodiments, the order of processing of theactive leaf nodes are such that the active leaf nodes with the highestbandwidth are processed first. In another embodiment, the order ofprocessing is based on priority among the nodes of the port tree. Onesuch embodiment is described in more detail below in conjunction withFIGS. 11A-11B. Control continues at block 906.

In block 906, data is outputted from the queue(s) associated with theselected node based on the allocated bandwidth. With reference to theexemplary embodiment of FIG. 2, the forwarding engine 202 outputs datafrom the queue(s) associated with the selected node based on theallocated bandwidth. As described above, in one embodiment, a given leafnode may have one to a number of queues associated therewith.Accordingly, in one embodiment, the allocated bandwidth for this node isequally distributed across the associated queues. Returning to FIG. 7Bto help illustrate, assume that the subscriber J node 530 has 10associated output queues. In such an embodiment, each output queueoutputs {fraction (1/10)} of the 100. Therefore, if the value of 100 isrepresentative of the number of megabits, each output queue for thesubscriber J node 530 outputs 10 megabits for this given cycle. Controlcontinues in block 908.

In block 908, a determination is made on whether there is a deficit atthe selected node. With reference to the exemplary embodiment of FIG. 2,the forwarding engine 202 makes the determination on whether there is adeficit at the selected node. The operations of make this determinationis described in more detail below in conjunction with the description ofblock 910.

In block 910, upon determining that there is a deficit at the selectednode from one to a number of queues during the outputting of data, adeficit count for the selected node is updated to reflect the deficit.With reference to the exemplary embodiment of FIG. 2, the forwardingengine 202 updates the deficit count for the selected node to reflectthe deficit of the output queues associated with the selected node.

To help illustrate, FIG. 10 illustrates an output queue storing a numberof packets, according to one embodiment of the invention. As shown, FIG.10 illustrates an output queue 1002 that includes packets of varyingsize. Beginning from the top, the output queue 1002 includes a packet1004 having a size of 75, a packet 1006 having a size of 150 and apacket 1008 having a size of 275.

Returning to FIG. 7B to help illustrate the output of packets from theoutput queue 1002, assume that the output queue 1002 is associated withthe subscriber I node 532. Accordingly, the output queue 1002 will havea bandwidth value of 100 (assuming that the output queue 1002 is theonly output queue associated with the subscriber I node 532). Inoperation, the forwarding engine 202 would output the packet that has asize of 75, thereby leaving a bandwidth value of 25. The next packet(the packet 1006) has a size of 150. Accordingly, there is not enoughavailable bandwidth in the current cycle to output the packet 1006.Therefore, the output queue 1002 has a deficit of 25, as a bandwidthvalue of 25 is unused.

In the subsequent cycle of operation, the available bandwidth includesthe deficit bandwidth of 25 and the distributed bandwidth for thecurrent cycle (100), thereby totaling a bandwidth value of 125. However,the size of the packet 1006 is 150. Accordingly, the forwarding engine202 does not output the packet 1006 because of the insufficientlydistributed bandwidth for the output queue 1002. Therefore, theforwarding engine 202 updates the deficit count for the output queue1002 such that the deficit is 125.

In the subsequent cycle of operation, the available bandwidth includesthe deficit bandwidth of 125 and the distributed bandwidth for thecurrent cycle (100), thereby totaling a bandwidth value of 225.Accordingly, the forwarding engine 202 outputs the packet 1006 (having asize of 150), leaving a bandwidth value of 75. The next packet (thepacket 1008) has a size of 275. Therefore, there is not enough bandwidthin the current cycle to output the packet 1008. Moreover, the forwardingengine 202 updates the deficit count for the output queue 1002, suchthat the deficit is 75. This determination of whether the output queuesfor a node has a deficit for a current cycle and the updating of thedeficit count continues across subsequent cycles. Returning to the flowdiagram 900, assuming that there is a deficit, the control continues atblock 902, where the determination is made regarding whether active leafnode(s) remain to be processed.

In block 912, upon determining that there is not a deficit at theselected node from one of the number of queues during the outputting ofdata, a determination is made on whether there is a surplus at theselected node. With reference to the exemplary embodiment of FIG. 2, theforwarding engine 202 makes the determination of whether there is asurplus at the selected node. In an embodiment, a surplus is defined asthat quantity of unused bandwidth that was allocated to the node for thegiven cycle. Returning to FIG. 7B to help illustrate, assume that thequeues associated with the subscriber I node 532 only include dataequaling 20 of the allocated 100. For example, assume that the queuesassociated with the subscriber I node 532 have been allocated 100megabits but that such queues only include 20 megabits. Accordingly, thesubscriber I node 532 has a surplus of 80. Upon determining that theselected node does not include a surplus, the control continues at block902, where the determination is made regarding whether active leafnode(s) remain to be processed.

In block 914, upon determining that the selected node does include asurplus, a determination is made of whether other sibling active nodesof the currently selected node are unprocessed. With reference to theexemplary embodiment of FIG. 2, the forwarding engine 202 makes thedetermination of whether other sibling active nodes of the currentlyselected node are unprocessed. Returning to FIG. 7B to help illustrate,assume that the subscriber B node 518 is the selected node and thatsubscriber C node 520 and the subscriber D node 522 have not beenselected to be processed in the current cycle of outputting data fromthis port. Accordingly, the subscriber B node 518 includes sibling nodesthat are active and not yet processed in the current cycle: thesubscriber C node 520 and the subscriber D node 522.

In block 916, upon determining that the selected node does include othersibling active nodes that are unprocessed, the surplus is redistributedto these sibling nodes. With reference to the exemplary embodiment ofFIG. 2, the forwarding engine 202 redistributes the surplus to thesesibling nodes. While this distribution can be performed a number ofdifferent ways, in one embodiment, the forwarding engine 202 distributesthe surplus equally across the associated queues of these sibling nodes.In other embodiments, a type of prioritization among the differentsibling nodes could allow for a different distribution (such as all orgreater portion is distributed to the queues of the sibling nodes havinga higher priority). Control continues at block 902, where thedetermination is made regarding whether active leaf node(s) remain to beprocessed.

In block 918, upon determining that the selected node does not includeother sibling active nodes that are unprocessed, the surplus is pushedto the parent node. With reference to the exemplary embodiment of FIG.2, the forwarding engine 202 pushes the surplus to the parent node.Returning to FIG. 7B to help illustrate, assume that the subscriber Dnode 522 has a surplus of bandwidth of 10 during the given cycle andthat the subscriber B node 518 and the subscriber C node 520 have beenprocessed. Accordingly, the forwarding engine 202 pushes the unusedbandwidth of 10 up to the parent node: the tunnel A node 508. Controlcontinues at block 920.

In block 920, a determination is made of whether the parent node (wherethe surplus is pushed) is the root node of the port tree. With referenceto the exemplary embodiment of FIG. 2, the forwarding engine 202 makesthe determination of whether the parent node (where the surplus ispushed) is the root node of the port tree. Returning to FIG. 7B to helpillustrate, if the context A node 504 is the current parent node towhich the surplus has been pushed and the context B node 506 has beendetermined not to have active children leaf nodes that are unprocessed(which is determine in block 922, which is described in more detailbelow), the surplus is pushed to the root node 502. Accordingly, if thesurplus reaches the root node 502, all of the active leaf nodes havebeen processed for the given cycle for this port. Therefore, the surplusfrom a given active leaf node cannot be redistributed for this givencycle. Upon determining that the parent node (where the surplus has beenpushed) is the root node of the port tree, the control continues atblock 902, where the determination is made regarding whether active leafnode(s) remain to be processed. In this situation, the determinationwould indicate that all of the active leaf node(s) have been processed,thereby completing the outputting of data from the port for this givencycle.

In block 922, upon determining that the parent node (where the surplushas been pushed) is not the root node of the port tree, a determinationis made of whether the siblings of the parent node have active childrenleaf nodes that are unprocessed. With reference to the exemplaryembodiment of FIG. 2, the forwarding engine 202 makes the determinationof whether the siblings of the parent node have active children leafnodes that are unprocessed. Returning to FIG. 7B to help illustrate,assume that a surplus of 50 has been pushed back to the tunnel A node508. The forwarding engine 202 would determine whether the activesibling nodes of the tunnel A node 508 (the tunnel B node 510 and thetunnel C node 512) have active children leaf nodes that are unprocessed.In this example, the forwarding engine 202 would determine that thesubscriber E node 524, the subscriber F node 528 are active childrenleaf nodes for the tunnel B node 510, while the subscriber I node 532and the subscriber J node 530 are active children leaf nodes for thetunnel C node 512. Accordingly, the forwarding engine 202 woulddetermine if any of the associated queues for the subscriber E node 524,the subscriber F node 528, the subscriber I node 532 or the subscriber Jnode 530 are unprocessed in the current cycle of outputting data fromthis given port.

In block 924, upon determining that the siblings of the parent node haveactive children leaf nodes that are unprocessed, the surplus isredistributed to these siblings' active leaf children nodes that areunprocessed. While a number of different approaches can be employed inthe redistribution of this surplus to the active leaf children nodes ofthe siblings of the parent that are unprocessed, in one embodiment, thesurplus is distributed equally across the different active leaf childrennodes. Returning to the example being described for block 922 above,assume that there is a surplus of 40 and that the subscriber E node 524,the subscriber F node 528, the subscriber I node 532 and the subscriberJ node 530 are unprocessed. Accordingly, the queues for each of thenodes 524, 528, 532 and 530 receive an additional bandwidth of 10.However, embodiments of the invention are not limited to such an equaldistribution of the surplus. In other embodiments, a type ofprioritization among the different sibling nodes could allow for adifferent distribution (such as all or greater portion being distributedto the queues of the sibling nodes having a higher priority). Controlcontinues at block 902, where the determination is made regardingwhether active leaf node(s) remain to be processed. Upon determiningthat the siblings of the parent node do not have active children leafnodes that are unprocessed, control continues in block 918 where thesurplus is pushed to the parent node. Accordingly, as described,embodiments of the invention allow for the redistribution of the unusedbandwidth for queues of a given node to other queues of other nodeswithin the port tree, thereby allowing for greater usage of thebandwidth for a given cycle.

A different embodiment for the operations of outputting of data from agiven port will now be described. FIGS. 11A-11B illustrate flow diagramsfor the outputting of data from a given port based on a hierarchy treeof data attributes, according to another embodiment of the invention.The operation of the flow diagrams 1100 and 1150 will be described withreference to the exemplary systems shown FIGS. 1-3. As will be describedin more detail below, the flow diagram 1150 illustrates a more detailedoperation of the block 1110 within the flow diagram 1100.

In block 1102, a determination made of whether there are active leafnode(s) that are unprocessed for the current cycle. With reference tothe exemplary embodiment of FIG. 2, the forwarding engine 202 makes thedetermination of whether there are active leaf node(s) that areunprocessed for the current cycle. As described above, in an embodiment,the forwarding engine 202 traverses the port tree for the given port toidentify the current active nodes within the tree. Accordingly, in anembodiment, the forwarding engine 202 tracks whether active leaf nodeshave been processed in a current cycle. Upon determining that there areno active leaf node(s) that are unprocessed for the current cycle, theoperations of the flow diagram 1100 are complete, thereby completing theoutputting of data for a given cycle for a port on a traffic card.

In block 1104, upon determining that there are active leaf nodes thatare unprocessed for the current cycle, a node at the highest level ofthe port tree having the highest priority and is active is selected.With reference to the exemplary embodiment of FIG. 2, the forwardingengine 202 selects the node at the highest level of the port tree havingthe highest priority and which is active. As described above, in oneembodiment, the nodes of the port tree include a number of attributes.In one embodiment, an attribute representing the priority level for thenode is associated with nodes of the port tree. In an embodiment, thispriority level/value represents a priority with reference to the othernodes at a given level. Returning to FIG. 7B to help illustrate, thetunnel A node 508 would have a value that is representative of apriority with reference to the tunnel B node 510, the tunnel C node 512and the tunnel D node 514. For example, the tunnel A node 508 could havea value of two; the tunnel B node 510 could have a value of one; thetunnel C node 512 could have a value of four; and the tunnel D node 512could have a value of three. Accordingly, the order of priority would beas follows: the tunnel B node 510, the tunnel A node 508, the tunnel Dnode 514 and the tunnel C node 512. However, embodiments of theinvention are not so limited. For example, in another embodiment, thenodes of the port tree could be assigned a priority value relative toall other nodes in the port tree. Control continues at block 1106.

In block 1106, a determination is made of whether the selected node is aleaf node. With reference to the exemplary embodiment of FIG. 2, theforwarding engine 202 makes the determination of whether the selectednode is a leaf node. As described above, in one embodiment, theforwarding engine 202 determines whether the selected node is a leafnode based on whether the selected node has children nodes.

In block 1108, upon determining that the selected node is not a leafnode, a node is selected among the active children nodes (of theselected node) having the highest priority. With reference to theexemplary embodiment of FIG. 2, the forwarding engine 202 selects thenode among the active children nodes (of the selected node) having thehighest priority. This recursive operation of selection of a nodecontinues until the selected node is a leaf node. Returning to FIG. 7Bto help illustrate, assume that the context A node 504 has a higherpriority than the context B node 506. Because the context A node is anon-leaf node, a selection is made between the tunnel A node 508 and thetunnel B node 510. Assuming that the tunnel A node 508 has a higherpriority and because the tunnel A node 508 is a non-leaf node, aselection is made (based on highest priority) among the subscriber Bnode 518, the subscriber C node 520 and the subscriber D node 522 (oneof which is the selected leaf node).

In block 1110, upon determining that the selected node is a leaf node,the selected node is processed. With reference to the exemplaryembodiment of FIG. 2, the forwarding engine 202 processes the selectednode. The operations of processing the selected node are described inmore detail below in conjunction with FIG. 11B. Control continues atblock 1112.

In block 1112, a determination is made of whether the selected node hasunprocessed active sibling nodes. With reference to the exemplaryembodiment of FIG. 2, the forwarding engine 202 determines whether theselected node has unprocessed active sibling nodes. Returning to FIG. 7Bto help illustrate, assume that the subscriber B node 518 is theselected node and that subscriber C node 520 and the subscriber D node522 have not been selected to be processed in the current cycle ofoutputting data from this port. Accordingly, the subscriber B node 518includes sibling nodes that are active and not yet processed in thecurrent cycle: the subscriber C node 520 and the subscriber D node 522.

In block 1114, upon determining that the selected node has unprocessedactive sibling nodes, the unprocessed active sibling node having thehighest priority is selected. With reference to the exemplary embodimentof FIG. 2, the forwarding engine 202 selects the unprocessed activesibling node having the highest priority. Returning to the example beingdescribed in conjunction with block 1112, assume that the subscriber Cnode 520 has a higher priority in comparison to the subscriber D node522. Accordingly, the subscriber C node 520 is selected from among thetwo nodes. Control continues at block 1110 where the selected node isprocessed. Therefore, this selection and processing at blocks 1114 and1110 continues until all of the unprocessed active sibling nodes havebeen processed.

In block 1116, upon determining that the selected node does not haveunprocessed active sibling nodes, a determination is made of whetherthere are active leaf node(s) that are unprocessed for the currentcycle. With reference to the exemplary embodiment of FIG. 2, theforwarding engine 202 makes the determination of whether there areactive leaf node(s) that are unprocessed for the current cycle. Asdescribed above, in an embodiment, the forwarding engine 202 traversesthe port tree for the given port to identify the current active nodeswithin the tree. Accordingly, in an embodiment, the forwarding engine202 tracks whether active leaf nodes have been processed in a currentcycle. Upon determining that there are no active leaf node(s) that areunprocessed for the current cycle, the operations of the flow diagram1100 are complete, thereby completing the outputting of data for a givencycle for a port on a traffic card.

In block 1118, upon determining that there are active leaf nodes thatare unprocessed for the current cycle, the active sibling node of theparent node of highest priority (that is unprocessed) is selected. Withreference to the exemplary embodiment of FIG. 2, the forwarding engine202 selects the active sibling node of the parent node of highestpriority (that is unprocessed). Returning to the example being describedin blocks 1112 and 1114 in conjunction with FIG. 7B to help illustrate,the tunnel A node 508 is the parent node. Assume that the tunnel B node510 and the tunnel C node 512 are unprocessed. Accordingly, the nodebetween the tunnel B node 510 and the tunnel C node 512 having thehighest priority is selected. Control continues at block 1106 where adetermination is made of whether the selected node is a leaf node.

Therefore, as described, the queues associated with the active leafnodes of the port tree are processed in an order that is based on apriority across the different nodes of the port tree. Such embodimentsallow for queues of higher priority to be processed first in comparisonto queues of lower priority for a given cycle of outputting data fromqueues of a given port.

A more detailed flow diagram of the operations associated withprocessing of selected nodes at block 1110 of FIG. 11A will now bedescribed. In particular, FIG. 11B illustrates a flow diagram forprocessing of selected nodes, according to one embodiment of theinvention.

In block 1152, data is outputted from the queue(s) associated with theselected node based on the allocated bandwidth. With reference to theexemplary embodiment of FIG. 2, the forwarding engine 202 outputs datafrom the queue(s) associated with the selected node based on theallocated bandwidth. As described above, in one embodiment, a given leafnode may have one to a number of queues associated therewith.Accordingly, in one embodiment, the allocated bandwidth for this node isequally distributed across the associated queues. Returning to FIG. 7Bto help illustrate, assume that the subscriber J node 530 has 10associated output queues. In such an embodiment, each output queueoutputs {fraction (1/10)} of the 100. Therefore, if the value of 100 isrepresentative of the number of megabits, each output queue for thesubscriber J node 530 outputs 10 megabits for this given cycle. Controlcontinues in block 1154.

In block 1154, a determination is made on whether there is a deficit atthe selected node. With reference to the exemplary embodiment of FIG. 2,the forwarding engine 202 makes the determination on whether there is adeficit at the selected node. A more detailed description of thisdetermination is set forth above in conjunction with block 908 of FIG.9.

In block 11156, upon determining that there is a deficit at the selectednode from one to a number of queues during the outputting of data, adeficit count for the selected node is updated to reflect the deficit.With reference to the exemplary embodiment of FIG. 2, the forwardingengine 202 updates a deficit count for the output queues associated withthe selected nodes to reflect the deficit. A more detailed descriptionof this updating of a deficit count is set forth above in conjunctionwith block 910 of FIG. 9. The control continues such that the operationsof the flow diagram 1150 are complete.

In block 1158, upon determining that there is not a deficit at theselected node from one of the number of queues during the outputting ofdata, a determination is made on whether there is a surplus at theselected node. With reference to the exemplary embodiment of FIG. 2, theforwarding engine 202 makes the determination of whether there is asurplus at the selected node. In an embodiment, a surplus is defined asthat quantity of unused bandwidth that was allocated to the node for thegiven cycle. Returning to FIG. 7B to help illustrate, assume that thequeues associated with the subscriber I node 532 only include dataequaling 20 of the allocated 100. For example, assume that the queuesassociated with the subscriber I node 532 have been allocated 100megabits but that such queues only include 20 megabits. Accordingly, thesubscriber I node 532 has a surplus of 80.

In block 1160, upon determining that the selected node does include asurplus, a determination is made of whether other sibling active nodesof the currently selected node are unprocessed. With referenced to theexemplary embodiment of FIG. 2, the forwarding engine 202 makes thedetermination of whether other sibling active nodes of the currentlyselected node are unprocessed. Returning to FIG. 7B to help illustrate,assume that the subscriber B node 518 is the selected node and thatsubscriber C node 520 and the subscriber D node 522 have not beenselected to be processed in the current cycle of outputting data fromthis port. Accordingly, the subscriber B node 518 includes sibling nodesthat are active and not yet processed in the current cycle: thesubscriber C node 520 and the subscriber D node 522.

In block 1162, upon determining that the selected node does includeother sibling active nodes that are unprocessed, the surplus isredistributed to these sibling nodes. With reference to the exemplaryembodiment of FIG. 2, the forwarding engine 202 redistributes thesurplus to these sibling nodes. While this distribution can be performeda number of different ways, in one embodiment, the forwarding engine 202distributes the surplus equally across the associated queues of thesesibling nodes. In other embodiments, a type of prioritization among thedifferent sibling nodes could allow for a different distribution (suchas all or greater portion being distributed to the queues of the siblingnodes having a higher priority). The control continues such that theoperations of the flow diagram 1150 are complete.

In block 1164, upon determining that the selected node does not includeother sibling active nodes that are unprocessed, the surplus is pushedto the parent node. With reference to the exemplary embodiment of FIG.2, the forwarding engine 202 pushes the surplus to the parent node.Returning to FIG. 7B to help illustrate, assume that the subscriber Dnode 522 has a surplus of bandwidth of 10 during the given cycle andthat the subscriber B node 518 and the subscriber C node 520 have beenprocessed. Accordingly, the forwarding engine 202 pushes the unusedbandwidth of 10 up to the parent node: the tunnel A node 508. Controlcontinues at block 1166.

In block 1166, a determination is made of whether the parent node (wherethe surplus is pushed) is the root node of the port tree. With referenceto the exemplary embodiment of FIG. 2, the forwarding engine 202 makesthe determination of whether the parent node (where the surplus ispushed) the root node of the port tree. Returning to FIG. 7B to helpillustrate, if the context A node 504 is the current parent node towhich the surplus has been pushed and the context B node 506 has beendetermined not to have active children leaf nodes that are unprocessed(which is determine in block 1168, which is described in more detailbelow), the surplus is pushed to the root node 502. Accordingly, if thesurplus reaches the root node 502, all of the active leaf nodes havebeen processed for the given cycle for this port. Therefore, the surplusfrom a given active leaf node cannot be redistributed for this givencycle. Upon determining that the parent node (where the surplus has beenpushed) is the root node of the port tree, the control continues suchthat the operations of the flow diagram 1150 are complete.

In block 1168, upon determining that the parent node (where the surplushas been pushed) is not the root node of the port tree, a determinationis made of whether the siblings of the parent node have active childrenleaf nodes that are unprocessed. With reference to the exemplaryembodiment of FIG. 2, the forwarding engine 202 makes the determinationof whether the siblings of the parent node have active children leafnodes that are unprocessed. Returning to FIG. 7B to help illustrate,assume that a surplus of 50 has been pushed back to the tunnel A node508. The forwarding engine 202 would determine whether the activesibling nodes of the tunnel A node 508 (the tunnel B node 510 and thetunnel C node 512) have active children leaf nodes that are unprocessed.In this example, the forwarding engine 202 would determine that thesubscriber E node 524, the subscriber F node 528 are active childrenleaf nodes for the tunnel B node 510, while the subscriber I node 532and the subscriber J node 530 are active children leaf nodes for thetunnel C node 512. Accordingly, the forwarding engine 202 woulddetermine if any of the associated queues for the subscriber E node 524,the subscriber F node 528, the subscriber I node 532 or the subscriber Jnode 530 are unprocessed in the current cycle of outputting data fromthis given port.

In block 1170, upon determining that the siblings of the parent nodehave active children leaf nodes that are unprocessed, the surplus isredistributed to these siblings' active leaf children nodes that areunprocessed. While a number of different approaches can be employed inthe redistribution of this surplus to the active leaf children nodes ofthe siblings of the parent that are unprocessed, in one embodiment, thesurplus is distributed equally across the different active leaf childrennodes. Returning to the example being described for block 1168 above,assume that there is a surplus of 40 and that the subscriber E node 524,the subscriber F node 528, the subscriber I node 532 and the subscriberJ node 530 are unprocessed. Accordingly, the queues for each of thenodes 524, 528, 532 and 530 receive an additional bandwidth of 10.However, embodiments of the invention are not limited to such an equaldistribution of the surplus. In other embodiments, a type ofprioritization among the different sibling nodes could allow for adifferent distribution (such as all or greater portion being distributedto the queues of the sibling nodes having a higher priority). Thecontrol continues such that the operations of the flow diagram 1150 arecomplete.

Upon determining that the siblings of the parent node do not have activechildren leaf nodes that are unprocessed, control continues in block1164 where the surplus is pushed to the parent node. Accordingly, asdescribed, embodiments of the invention allow for the redistribution ofthe unused bandwidth for queues of a given node to other queues of othernodes within the port tree, thereby allowing for greater usage of thebandwidth for a given cycle.

The servers as well as the traffic cards, forwarding cards and controlcards included in the different network elements include memories,processors and/or Application Specific Integrated Circuits (ASICs). Suchmemory includes a machine-readable medium on which is stored a set ofinstructions (i.e., software) embodying any one, or all, of themethodologies described herein. Software can reside, completely or atleast partially, within this memory and/or within the processor and/orASICs. For the purposes of this specification, the term“machine-readable medium” shall be taken to include any mechanism thatprovides (i.e., stores and/or transmits) information in a form readableby a machine (e.g., a computer). For example, a machine-readable mediumincludes read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; flash memory devices;electrical, optical, acoustical or other form of propagated signals(e.g., carrier waves, infrared signals, digital signals, etc.); etc.

Thus, a method and apparatus for hierarchy tree-based quality of serviceclassification for packet processing have been described. Although thepresent invention has been described with reference to specificexemplary embodiments, it will be evident that various modifications andchanges may be made to these embodiments without departing from thebroader spirit and scope of the invention. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

What is claimed is:
 1. A method comprising: receiving a packet of anumber of packets for storage into an egress port, the egress porthaving a number of queues associated with nodes of a hierarchy tree, thehierarchy tree having a level of nodes associated with contexts for thenumber of packets; and storing the packet into a queue of the number ofqueues of the egress port, the queue corresponding to a node within thehierarchy tree associated with a subscriber from which the packetoriginates, wherein the node associated with the subscriber isdetermined based on a tunnel through which the packets traverse via thehierarchy tree, and wherein the tunnel is determined based on a nodeassociated with the context of the packets via the hierarchy tree. 2.The method of claim 1, wherein the hierarchy tree includes a level ofnodes associated with tunnels that the number of packets are totraverse.
 3. The method of claim 1, wherein the hierarchy tree includesa level of nodes associated with subscribers from which the packetsoriginate.
 4. The method of claim 1, wherein the number of queues areassociated with the leaf nodes of the hierarchy tree, the leaf nodes ofthe hierarchy tree associated with subscribers from which the packetsoriginate.
 5. A method comprising: receiving a packet of a number ofpackets for storage into an egress port having a number of queues;retrieving a hierarchy tree associated with the egress port from amemory; locating a node in the hierarchy tree at a context level that isassociated with a context for the packet; locating a node in thehierarchy tree, which is a child of the located node at the contextlevel, at a tunnel level that is associated with a tunnel for thepacket; locating a node in the hierarchy tree, which is a child of thelocated node at the tunnel level, at a subscriber level that isassociated with a subscriber for the packet; and storing the packet intoone of a number of queues associated with the node at the subscriberlevel, upon determining that the node at the subscriber level includes anumber of queues.
 6. The method of claim 5, wherein storing the packetinto one of the number of queues associated with the node at thesubscriber level includes storing the packet into one of the number ofqueues associated with the node at the subscriber level based onStochastic Fair Queuing.
 7. The method of claim 5, wherein the number ofqueues are associated with different qualities of service.
 8. A networkelement comprising: a traffic card that includes an egress port, theegress port to include a number of egress queues to store a number ofdata packets; and a forwarding card that includes, a memory to store aport tree having a context level of nodes, wherein each node at thecontext level is associated with a context for the number of datapackets; and a forwarding engine to store a data packet of the number ofdata packets into an egress queue of the number of egress queues basedon the context of the data packet, wherein the egress queue isdetermined based on a subscriber from which the data packet originates,wherein the subscriber is determined based on a tunnel through which thepackets traverse via the hierarchy tree, and wherein the tunnel isdetermined based on a node associated with the context of the packetsvia the port tree.
 9. The network element of claim 8, wherein the numberof egress queues are associated with different levels of quality ofservice.
 10. The network element of claim 8, wherein the port tree has atunnel level of nodes, where each node at the tunnel level is associatedwith a tunnel that the number of data packets are transmitted.
 11. Anetwork element comprising: a traffic card that includes an egress port,the egress port to include a number of egress queues to store a numberof data packets; and a forwarding card that includes, a memory to storea port tree having a context level of nodes, wherein each node at thecontext level is associated with a context for the number of datapackets; and a forwarding engine to store a data packet of the number ofdata packets into an egress queue of the number of egress queues basedon the context of the data packet, wherein the port tree has a tunnellevel of nodes, where each node at the tunnel level is associated with atunnel that the number of data packets are transmitted, and wherein theport tree has a subscriber level of nodes, wherein each node at thesubscriber level is associated with a subscriber from which the datapackets originate.
 12. The network element of claim 11, wherein thenodes of the tunnel level are children nodes of the nodes at the contextlevel and wherein the nodes of the subscriber level are children nodesof the nodes at the tunnel level.
 13. An apparatus comprising: a memoryto store a port tree for a ports of a network element, the port treehaving a context level of nodes, wherein each node at the context levelis associated with a context for the number of data packets, the policytree having a tunnel level of nodes, wherein each node at the tunnellevel is associated with a tunnel that the number of data packets aretransmitted, wherein the nodes at the tunnel level are children nodes ofthe nodes at the context level, the port tree having a subscriber level,each node at the subscriber level is associated with a subscriber fromwhich the data packet originate, wherein the nodes at the subscriberlevel are children nodes at the tunnel level; and a forwarding engine totraverse the port tree and to store a data packet of the number of datapackets into a queue of the port based on an associated context, anassociated tunnel and an associated subscriber of the data packet. 14.The apparatus of claim 13, wherein the memory is to store a policy treefor one to a number of different ports, wherein the port tree isinstantiated based on the policy tree.
 15. The apparatus of claim 13,wherein a node at the subscriber level is a leaf node of the port treeand is associated with a number of queues of the port.
 16. The apparatusof claim 13, wherein each node of the port tree is associated with aportion of the allocated bandwidth for the port.
 17. A machine-readablemedium having stored thereon a policy tree, the policy tree comprising:a number of non-leaf nodes within a first level of the policy tree,wherein each of the number of non-leaf nodes within the first level isassociated with different contexts for packets for packet processingwithin a network element; a number of non-leaf nodes within a secondlevel of the policy tree, wherein each of the number of non-leaf nodeswithin the second level is associated with a tunnel for packetprocessing within the network element; wherein one to a number of thenon-leaf nodes within the second level are children of the non-leafnodes within the first level; and a number of leaf nodes within a thirdlevel of the policy tree, wherein each of the number of leaf nodes isassociated with a subscriber for packet processing within the networkelement, wherein one to a number of the leaf nodes are children of thenon-leaf nodes within the second level.
 18. The machine-readable mediumof claim 17, wherein each node of the policy tree is associated with aportion of the allocated bandwidth for a port for the network element.19. The machine-readable medium of claim 18 having stored thereon anumber of port trees based on instantiations of the policy tree.
 20. Amachine-readable medium that provides instructions, which when executedby a machine, cause said machine to perform operations comprising:receiving a packet of a number of packets for storage into an egressport, the egress port having a number of queues associated with nodes ofa hierarchy tree, the hierarchy tree having a level of nodes associatedwith contexts for the number of packets; and storing the packet into aqueue of the number of queues of the egress port, the queuecorresponding to a node within the hierarchy tree associated with asubscriber from which the packet originates, wherein the node associatedwith the subscriber is determined based on a tunnel through which thepackets traverse via the hierarchy tree, and wherein the tunnel isdetermined based on a node associated with the context of the packetsvia the hierarchy tree.
 21. The machine-readable medium of claim 20,wherein the hierarchy tree includes a level of nodes associated withtunnels that the number of packets are to traverse.
 22. Themachine-readable medium of claim 20, wherein the hierarchy tree includesa level of nodes associated with subscribers from which the packetsoriginate.
 23. The machine-readable medium of claim 20, wherein thenumber of queues are associated with the leaf nodes of the hierarchytree, the leaf nodes of the hierarchy tree associated with subscribersfrom which the packets originate.
 24. A machine-readable medium thatprovides instructions, which when executed by a machine, cause saidmachine to perform operations comprising: receiving a packet of a numberof packets for storage into an egress port having a number of queues;retrieving a hierarchy tree associated with the egress port from amemory; locating a node in the hierarchy tree at a context level that isassociated with a context for the packet; locating a node in thehierarchy tree, which is a child of the located node at the contextlevel, at a tunnel level that is associated with a tunnel for thepacket; locating a node in the hierarchy tree, which is a child of thelocated node at the tunnel level, at a subscriber level that isassociated with a subscriber for the packet; and storing the packet intoone of a number of queues associated with the node at the subscriberlevel, upon determining that the node at the subscriber level includes anumber of queues.
 25. The machine-readable medium of claim 24, whereinstoring the packet into one of the number of queues associated with thenode at the subscriber level includes storing the packet into one of thenumber of queues associated with the node at the subscriber level basedon Stochastic Fair Queuing.
 26. The machine-readable medium of claim 24,wherein the number of queues are associated with different qualities ofservice.